-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[ENH] Voyageai integration update #5598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[ENH] Voyageai integration update #5598
Conversation
Adding token counting and flexible batch size Extending the tests
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
|
Add VoyageAI contextual, multimodal, token-counting & batching support This PR substantially extends the VoyageAI integration. The original Key Changes• Refactor Affected Areas• This summary was automatically generated by @propel-code-bot |
chromadb/utils/embedding_functions/voyageai_embedding_function.py
Outdated
Show resolved
Hide resolved
Adding token counting and flexible batch size Extending the tests
Co-authored-by: propel-code-bot[bot] <203372662+propel-code-bot[bot]@users.noreply.github.com>
|
I removed the default model. I'm aware that this might cause problems, but i think it would be better if the user passes the model name intentionally to avoid any issue. |
|
@tazarov, can you please take a look? How to push this PR forward? |
|
@tazarov, can you please take a look? How would you like to push this PR forward? |
Description of changes
Voyageai contextual and multimodal
Adding token counting
Adding more tests
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rustMigration plan
Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?
No
Observability plan
What is the plan to instrument and monitor this change?
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?